home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
mnet210.zip
/
MNET.DOC
< prev
next >
Wrap
Text File
|
1994-06-29
|
37KB
|
737 lines
MNET v2.10 - Mail Packet Conversion Utility for Node Operation
on a QWK-based Mail Network
Copyright (C) 1992-94 Newark Connections/MAKAI Software
All rights reserved.
==========================================================================
Before we can get started, we need to run through the now-familiar
notices and disclaimers:
MNET is copyrighted software from MAKAI Software. It is not public
domain or freeware, but rather is released as uncrippled shareware.
You are free to try MNET to see if it meets your needs, but if you
decide to continue to use MNET, you are required to register the
software with MAKAI Software. See Appendix A of this file, or the
separate file REGISTER.DOC, included with this package.
While we have attempted to produce a useful piece of bugfee software
(which runs quite well on our system here, by the way), MNET is
released as-is with no guarantees of performance. YOU USE MNET AT YOUR
OWN RISK, and the authors will not be held accountable for any damages
resulting from its use.
The MNET package (MNET210.ZIP) may be distributed freely (in unmodified
form) to friends, associates, and bulletin boards. Re-archiving into
your favorite format (ARJ, LZH, etc) is permitted, provided that the
entire package (and all documentation) is included in the re-archiving
process, and no files are modified. If you received this package in
some other format than MNET210.ZIP, or the .ZIP file does not have Chip
Morrow's or Doug Wilson's -AV verification, then you did not receive an
original copy. Please see the appendices on how to obtain a copy of
MNET directly from a MAKAI Software distribution site.
If you are a registered user of MNET, do *NOT* distribute the
registration code that you received from us. This is your own personal
registration, and is not for distribution.
If you are a shareware distributor/dealer, a nominal disk copying and
handling fee is permitted.
And one more necessary announcement:
****************************************************************
* IMPORTANT NOTE: Many established networks, such as FIDONet, *
* RBBSNet, and RIME do not permit unauthorized distribution of *
* their message bases. ** DO NOT ** use MNET to transfer such *
* conferences without first obtaining permission from proper *
* authorities. *
****************************************************************
MNET v2.10 QWK-Network File Conversion Utility
- Page 2 -
----------------------------------------------------------------------
FOREWARD
----------------------------------------------------------------------
Some years ago Mark "Sparky" Herring devised a system for creating packets
of mail from electronic bulletin boards for the purpose of downloading and
reading/replying offline. The "QWK" format he established has become a
standard used by many offline messaging systems. Although originally
designed for use by individual callers to a bbs, this format has been
extended and adapted for inter-bbs message networking as well.
Normally, each bbs participating in a QWK-based network must have its own
software which will take a message "QWK" packet from the host board and
toss it the node board's native message base. The same software would
normally be used to scan the node's message base for outgoing messages and
place them into a "REP" packet for uploading back to the host board.
Since the software operated by the node must interface with the node's own
message base, each type of bbs generally needs its own specialized QWK-net
handling software.
There are many boards out there which have QWK-based mail facilities for
use by its callers, but which do not have specialized software to process
QWK-net packets. That's where MNET comes in. MNET is simply a net-aware
mail conversion utility that takes QWK packets from the host and converts
them to REP packets which may be uploaded to the node's standard QWK mail
facilities. Similarly, MNET can convert a QWK packet of outgoing mail
from the node into a REP which can be uploaded to the host. Since the
node's standard QWK mail facility does all the interfacing with node's
message base, no additional specialized software is required. MNET allows
any bulletin board with QWK-compatible offline mail capability the ability
to be a node in a QWK-based message network.
MNET was originally developed for use in conjunction with MAKAI Software's
Mail Manager +Plus+ QWK mail door for RBBS systems, but it is now in use
on many different bbs systems around the world.
--------------------------------------------------------------------------
GENERAL OVERVIEW
--------------------------------------------------------------------------
Let's assign some sample packet names to use for purposes of illustration:
- You log onto the host's board and download a "net status" packet
called "HOST.QWK".
- You are networking the "SPECIAL" conference, which is area #3 on
host's system.
- The REP packets that you send to your host will be named "HOST.REP".
- Your board uses the filenames "NODE.QWK" and "NODE.REP" for QWK and
REP packets transferred.
- The networked "SPECIAL" conference is area #15 on your system.
MNET v2.10 QWK-Network File Conversion Utility
- Page 3 -
The MNET.EXE utility will allow you to transfer the messages contained in
HOST.QWK into your system, and to convert any outbound messages from your
system into a HOST.REP file that you can upload to the host.
All the fun part of pulling this off is on your end:
1) You fire up the your bbs QWK mail facilities and extract a QWK packet
of the messages to be exported. Using the naming conventions from
above, you would create a packet named NODE.QWK.
2) The host system can't do anything with NODE.QWK, so you use our MNET
utility to convert it to HOST.REP.
3) Call up the host board, extract and download a new HOST.QWK and upload
your HOST.REP reply packet. Depending on how your host is set up, you
may need to call in under a special user name which the host sets up
for you in order to grant you net access. Also note that, depending on
how your host's system handles net packets, it may be necessary for you
to reset message pointers after you upload your REP so as not to
receive those same messages back in your next QWK packet. Check with
your host sysop on how this must be handled on that particular system.
4) Back at your end, you use MNET to convert HOST.QWK that you just
downloaded to NODE.REP.
5) Go back into the QWK mail facilities for your board and upload the
newly imported messages as NODE.REP. Depending on your system, you may
need to update your message pointers after uploading the rep so as not
to export those same messages in your next packet.
6) Repeat unto infinity.
Now, you would probably imbellish this to make a call that does all of
this at once (i.e. - Send up HOST.REP and download HOST.QWK in the same
session).
Graphically, this might look like:
MNET v2.10 QWK-Network File Conversion Utility